Planning system for autonomous operation

ABSTRACT

A planning system ( 201 ) for scheduling the operation of autonomous entities within a defined geographical region. The planning system operates at a region plan level ( 301 ) for strategic planning across the geographical region, at an operation plan level ( 302 ) for operations to be performed by autonomous entities in localised zones having operation-defined geographical boundaries, and at a task plan level ( 303 ) in which processing is undertaken in respect of specific tasks to be performed by the autonomous entities, in undertaking the operations.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation application of U.S. patentapplication Ser. No. 13/318,469, filed Nov. 1, 2011, which is a U.S.National Phase application under 35 U.S.C. § 371 of InternationalApplication No. PCT/AU2010/000497, filed Apr. 30, 2010, entitledPLANNING SYSTEM FOR AUTONOMOUS OPERATION, which claims priority toAustralian patent application number 2009901935, filed May 1, 2009.

FIELD OF THE INVENTION

This invention relates to the conducting of integrated operations withina defined geographical region and, in particular, to operationsinvolving autonomous equipment. The invention has various applicationsand, in one of its possible embodiments, has application to a mineautomation system

BACKGROUND OF THE INVENTION

There is an increasing use of control systems to automate industrialprocesses or machinery, as automation may provide greater efficiency andsafety. As the complexity of the processes or machinery increases, themore complex the automation system becomes. This is particularly sowhere autonomous operations are involved.

One example of a complex application where autonomous operations may beused is in mining. Conventional open pit mining, for example ofmetal-bearing mineral or rock, normally involves the progressiveaccessing of an ore body followed by drilling, blasting, loading andhaulage of the released material. In the case of iron ore it is mined inlarge blocks from a series of benches and the various mining activities(other than blasting) are performed concurrently, resulting in diverseequipment, and often personnel, being present simultaneously in the minesite. A bench of ore typically 40 m long×20 m deep×10 m high andcontaining in the order of 8 kilotonnes of ore is first drilled to forma pattern of blast holes and the drilling residue is analysed, as onestep in a more extensive analysis, to determine whether the material tobe blasted comprises, on average, high grade ore, low grade ore or wastematerial. The blasted material is collected by shovels, excavatorsand/or front end haul loaders, loaded into haul trucks and transportedfrom the mine pit. The material is then processed outside of the minepit, depending upon grade determination; waste material typically beingused as mine fill, low grade ore being stockpiled or blended with highgrade ore, and high grade ore being processed further as required toform a marketable product.

Autonomous operations have to date been adopted to a very limited extenton mine sites. Examples include the operation of automated haulagevehicles under remote control from centralised control systems.

SUMMARY OF THE INVENTION

The present invention seeks to provide for more extensive automationinvolving the integration of different autonomous systems.

According to a first aspect of the invention there is provided aplanning system for scheduling the operation of autonomous entitieswithin a defined geographical region, the planning system operating atthree hierarchical levels:

a) a region plan level in which processing is undertaken in respect ofplanning operations at a strategic level across the geographical region,b) an operation plan level in which processing is undertaken in respectof entity-related operations to be performed by autonomous entities inselected localised zones of the geographical region havingoperation-defined geographical boundaries, andc) a task plan level in which processing is undertaken in respect ofspecific tasks to be performed by said autonomous entities, inundertaking the operationswherein the operation of the planning system comprises generatingcontrol information defining activities at the region plan level, theoperation plan level and the task plan level and making the controlinformation available to the autonomous entities for implementation.

According to a further aspect of the invention there is provided ahierarchical planning system for scheduling the operation of a pluralityof autonomous entities within a defined geographical region, comprising:

a) a region planning module for generating a region-wide plan comprisingat least one job to which one or more autonomous entities are assigned,wherein the geographical region comprises a plurality of localised zoneshaving operation-defined geographic boundaries and at least one of theautonomous entities is a mobile entity that, is required to move betweenlocalised zones to implement the region-wide plan;

b) a job planning module associated with each job in the region-wideplan for generating a job plan comprising a series of tasks for theautonomous entities assigned to the associated job; and

c) a task planning module associated with each autonomous entity forgenerating a task plan comprising a set of actions to be performed bythe associated autonomous entity as part of the associated job.

The invention will be more fully understood from the followingdescription of an exemplary embodiment in the form of a complete MineAutomation System (MAS). The description is provided by way ofillustration and with reference to diagrammatic representations shown inthe accompanying drawings.

As used herein, except where the context requires otherwise, the term“comprise” and variations of the term, such as “comprising”, “comprises”and “comprised”, are not intended to exclude further additives,components, integers or steps.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 is a schematic representation of a high-level architecture of anintegrated automation system for a mine including an implementation of aMAS system according to one embodiment of the invention;

FIG. 2 illustrates the Mine Automation System (MAS) of the system ofFIG. 1;

FIG. 3 is a diagrammatic representation of a Mine Planning System (MPS)of the MAS of FIG. 2;

FIG. 4 is a diagrammatic representation of a Mine Picture CompilationSystem (MPCS) of the MAS of FIG. 2;

FIG. 5 shows a logical schematic of a fusion system of the MPCS of FIG.4;

FIG. 6 is a diagrammatic representation of a Mine Control System (MCS)of the MAS of FIG. 2;

FIG. 7 is a diagrammatic representation of a high level state machinefor the MAS of FIG. 2;

FIG. 8 is a diagrammatic representation of a state machine for a“Run_MAS” state of the state machine of FIG. 7;

FIG. 9 illustrates a transition example for an entity seeking transitionfrom a start location in B to an end location in C according to oneembodiment of the invention;

FIGS. 10a-e illustrate information flow during the transition shown inFIG. 9;

FIGS. 10f-h illustrate temporal sequences for the transition shown inFIG. 9;

FIG. 11 is a diagrammatic representation of a system according to oneembodiment of the invention;

FIG. 12 is a diagrammatic representation of an MPS according to oneembodiment of the invention;

FIG. 13 is a diagrammatic representation of an MCS topology according toone embodiment of the invention;

FIG. 14 is a diagrammatic representation of communication between eachTask Planner of FIG. 12 and the MCS of FIG. 13;

FIG. 15 is a diagrammatic representation of MPCS deployment according toone embodiment of the invention;

FIG. 16 illustrates control communications to an MPCS plug-in of FIG. 15in the MCS of FIG. 13;

FIG. 17 illustrates communication between the MPCS of FIG. 15, the MCSof FIG. 13 and mine equipment shown in FIG. 11;

FIG. 18 is a diagrammatic representation of a configuration of the MASaccording to the components described in FIGS. 11-17; and

FIG. 19 is an example of a graphical representation of a geographicalregion.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Broadly defined, the systems and methods described below enableautonomous operations to be effected within a defined geographicalregion. A plurality of localised zones having operation-definedgeographical boundaries are established within the region and autonomousoperating systems perform specific autonomous operations within thelocalised zones, the autonomous operating systems controlling one ormore autonomous entities, for example self-guided and operated vehicles.An autonomous system of a management party may be integrated with theautonomous operating systems. An operator may (but need not necessarily)also be enabled to exercise overriding control over the management partyautonomous system and, by way of that system, over the autonomousoperating systems.

The expression “operation-defined geographical boundaries” is to beunderstood as meaning boundaries that embrace zones in which operationsare conducted or in which operations may from time to time be conducted.For example, in the context of a mine site a boundary that embraces anactive bench loading zone may be operation-defining, as may be one thatsurrounds a static roadway along which operational haul trucks maytravel.

The described systems and methods have various applications; for exampleto a method of conducting autonomous operations in mining, agricultural,forestry, marine or military applications where autonomous operationsmay be conducted in at least one zone (that has an operation-definedgeographical boundary) within a defined region. In the context of anagricultural application, for example, the invention may be employed tofacilitate the implementation of controls in relation to autonomousagricultural machinery that is operated in localised zones of a largeragricultural property.

As also indicated previously, the described systems and methods mayhave, and in accordance with one exemplary embodiment do have,application in mining, and the invention may incorporate a mine controlsystem (“MCS”). As such, the MCS may optionally be integrated into amine automation system (“MAS”), with other components of the MASoptionally comprising a mine planning system (“MPS”) and a mine analysissystem which is referred to herein as a mine picture compilation system(“MPCS” or “MPC”). Reference may be made to Tables 12 and 13 for alisting of these and other acronyms and terminology used throughout thisspecification.

The system integrates operation units (third party systems of equipmentdeployed in the mine which may have their own automation systems), aPicture Compilation System, a Planning System and a Control System.

The MAS concept of operations entails bounded, uniquely definedlocalised zones or spatial regions within the mine region employingautomation and/or operating personnel. Each of these zones is consideredas an Island of Automation (IoA), that may effectively change locationwith time or whose boundary may change in shape, each operating locallywith its own set of entry points, exit points, rules and constraints.

For safety, there should be strict separation between the IoAs, with anentity being only under the control of a single IoA at any given timeand the described methods provide a means for controlling interactions.A combination of physical barriers, such as windrows and fencing, or ofvirtual “barriers”, such as GPS-based mapping, may be used to separatethe islands/zones. As all entities in the mine will typically have aself-localisation capability, a virtual barrier can be configured toalarm or shut down operations when entities deviate from their operatingregions.

At the highest level, the entire mine can be considered as a single IoA.A hierarchy of sub-regional islands can then be defined to encapsulatespecific working areas. For example, separate IoAs may be creatednotionally within the mine for a road network, a bench to be drilled andan area under excavation. Also, it may be desirable in a given minesituation to create a nested hierarchy of smaller IoAs within theseareas, should that be required. Transition into and out of an IoA isstrictly controlled and the concept of a transition zone (describedbelow with reference to FIGS. 9 and 10) is used to define the regionaround entry and exit points where transitions are managed. A role ofthese transition zones is to provide strict bounds to the areas wherecontrol handover can occur and to ensure that an entity is not operatingwithout being under the control of an authenticated system.

The MAS and its components can be implemented in a centralised,distributed or decentralised architecture. For example, the MPC and NCSsystems may be distributed or decentralised such that each IoA may havea dedicated control unit and MPC instance responsible for that IoA. Thesame system may also be implemented in a centralised architecture. Forexample the models generated by the Mine Picture Compilation System maybe stored on a centralised database, or the control of all IoAs may becalculated by a centralised controller and communicated to each IoA.

The primary functional building blocks of the described systems areimplemented in software. Where applicable, terminology is thus usedthroughout this specification to describe a software implementation.

The software required for the Picture Compilation System, PlanningSystem and Control System may be implemented with the aid of appropriatecomputer hardware in the form of a computing system such as a server.The server comprises suitable components necessary to receive, store andexecute appropriate computer instructions. The components may include aprocessing unit, memory, storage and an input-output interface. Standardcomputing hardware also includes a bus for communication amongsthardware components. One example of a suitable system is the DellPowerEdge M600 server, which may be housed in a Dell PowerEdge M1000eenclosure.

The automation functionality in the operation units may be implementedusing appropriate computer hardware and software. Software that needs tobe run on units in harsh conditions, for example in a mine, may be runon an embedded computer that has a mounted power supply, the embeddedcomputer comprising suitable components necessary to receive, store andexecute appropriate computer instructions. The components may include aprocessing unit, memory, storage and an input-output interface. Oneexample of a suitable system is the Ampro LittleBoard™800 single boardcomputer provided by Ampro Computers, Inc of San Jose, Calif. If theautomation units are deployed in harsh conditions, the computer systemmay be housed in a protective enclosure.

Communication between units, and between the operation units and thecomponents of the MAS may be implemented using a wireless communicationsystem that supports bidirectional communication.

1. Integrated Automation System

FIG. 1 illustrates a high level architecture 100 of an integratedautomation system for a mine. Key elements of this system include:

-   -   Software subsystems    -   Embedded hardware systems    -   Sensor systems    -   Data fusion, processing and storage systems    -   Intelligent planning, scheduling and control subsystems    -   Autonomous vehicles    -   Communication networks.

The core element of the autonomous system is the Mine Automation System(MAS) 101, which is a distributed real-time automation system. The MASincludes interfaces, sub-systems, logical connections and informationdissemination links to interface and support operators and generic thirdparty automation and information elements.

1.1. Operator Control

Human oversight of autonomous operations is an aspect of the systemarchitecture and this is illustrated in FIG. 1, where the operatorelement 102 is used to encapsulate all human interaction with the MAS101. This may include operators physically distributed throughout themine site, at a central mine control room and at a remote operationscentre, (ROC) (not shown).

The MAS architecture may be structured to allow any element in thesystem to be queried by human operators 102 and operator roles may bedefined to allow control and monitoring of all autonomous processes,with authority to supersede automation systems or shut them down. Thislevel of control is provided for emergency and safety cases, anddesirably should not be exercised during routine operations.

Key elements of operators' roles may include:

-   -   Monitoring the status of entities in the mine;    -   Managing, planning and scheduling operations in the mine;    -   Handling and managing emergency situations;    -   Regulatory assessment of information systems.

1.1.1. Link L-1

Table 1 shows the information interactions between human operators 102and the MAS 101. Information exchanges as described for all the links inthe system (L-1 to L-11) are described only through the type ofinformation that is transmitted, and not the specific message format orprotocol.

The location of Link L-1 is illustrated in FIG. 1. The human operators102 can add, edit, update or delete information in any sub-system of theMAS 101. The operators have direct interaction to the MPS 201, MCS 203and the MPCS 202 shown in FIG. 2 and have a capability to authorise orreject data or any activity in these sub-systems.

TABLE 1 Information exchanges between the MAS 101 and human operators102 (Link L-1). L-1 Source Human decision makers/planners DestinationMine Automation System (MAS) L-1.1 Information to MPS. L-1.1.1Information about the Mine Plan. L-1.1.2 Information about the Job Plan.L-1.1.3 Information about the Task Plan. L-1.2 Information to MPCS.L-1.2.1 Information about managing MPC instances. L-1.2.2 Informationabout the Equipment Model. L-1.2.3 Information about the In-GroundModel. L-1.2.4 Information about the Out-of-Ground Model. L-1.3Information to MCS. L-1.3.1 Information about managing xIC Instances.L-1.3.2 Information about control plans of entities operating in themine. Source Mine Automation System (MAS) Destination Human decisionmakers/planners L-1.4 Information from the MPS. L-1.4.1 Informationabout the Mine Plan. L-1.4.2 Information about the Job Plan. L-1.4.3Information about the Task Plan. L-1.5 Information from the MPCS.L-1.5.1 Information about the MPCS configuration. L-1.5.2 Informationabout the Equipment model. L-1.5.3 Information about the In-Groundmodel. L-1.5.4 Information about Out-of-Ground Model. L-1.6 Informationfrom the MCS. L-1.6.1 Information about the MCS configuration. L-1.6.2Information about the status of control plans of entities operating inthe mine.

1.2. Third Party Systems

The MAS 101 architecture is arranged to support information from bothexisting and future systems, which may be third-party systems andservices 103. This is managed through the use of flexible plug-ininterface components within the system 100. The plug-ins may be writtento support transformations between the representations of externalsystems 103 and elements of the MAS 101 and, as new systems becomeavailable, new plug-ins may be developed to ensure compatibility.

The systems 103 that interface with the MAS 101 may include informationsystems and services 105 and/or automation systems and services 104. Anexample of a third party automation system is a vehicle with its ownautonomous operating system, including its own communications protocolsfor communicating commands to the autonomous system. Examples of thirdparty information systems and services 105 include databases andplanning systems. Some third party information systems 105 may notnatively support the information formats used within the MAS 101. Ifrequired, plug-in interfaces for the MAS 101 may provide a set oftransformations to convert information formats.

The MAS 101 may interface with third party automation systems andservice 104 that provide specialised machinery and services such as:

-   -   Autonomous Haul Trucks;    -   Resource schedulers;    -   Specialised sensor systems and analysis methods; and    -   Mine-wide communication services.

The MAS 101 architecture facilitates key interface points for theintegration of these third party automation systems 104. Those that meetinterface specifications should integrate seamlessly.

1.2.1. Link L-2

Table 2 shows the interactions between Third Party Systems and Services103 and the MAS 101. The location of Link L-2 is illustrated in FIG. 1.The Third Party Systems are divided into information 105 and automation104 categories.

Information transferred to and received from Third Party Systems andServices 103 is converted to a format compatible to the MAS 101. Thiscan be performed through native support for MAS information formatswithin third party systems 103, or the use of special plug-in interfaceswithin the MAS 101.

Third Party Systems and Services 103 can interact with the MPS 201 forplanning and scheduling functions, the MPCS 202 for information fusionof geometric, geological and equipment information and the MCS 203 forcontrol and monitoring purposes.

TABLE 2 Information exchanges between the MAS 101 and third partysystems and services 103 (Link L-2). L-2 Source Mine Automation System(MAS) Destination Third Party Systems and Services L-2.1 Information tothe Third Party Information Systems and Services L-2.1.1 Informationabout the MPCS. L-2.1.2 Information about the MCS. L-2.1.3 Informationabout the MPS. L-2.2 Information to the Third Party Automation Systemsand Services L-2.2.1 Information about the MPCS. L-2.2.2 Informationabout the MCS. L-2.2.3 Information about the MPS. Source Third PartySystems and Services Destination Mine Automation System (MAS) L-2.3Information to MPS. L-2.4 Information to MCS. L-2.5 Information to MPCS.

1.3. Mine Automation System Architecture

The MAS 101, shown in more detail in FIG. 2, comprises an integratedsystem that includes planning, estimation and control sub-systems whichnormally will be distributed spatially throughout a mine operation.Specifically, the main functional modules of the MAS are the:

1. Mine Planning System, MPS 201,

2. Mine Picture Compilation System MPCS, 202, and

3. Mine Control System, MCS 203.

These systems operate in a fully connected topology as illustrated inFIG. 2.

Important dependencies exist between these elements of the system; theMCS 203 having a dependency on the MPCS 202, and the MPS 201 havingdependencies on both the MPCS 202 and MCS 203. Given this, the order ofdeployment when running the MAS 101 is:

1. MPCS 202;

2. MCS 203; then

3. MPS 201.

1.3.1. Link L-3

Information exchanges between the MPS 201 and the MPCS 202 occur throughLink L-3 and are shown in Table 3. The location of this link isillustrated in FIG. 2.

TABLE 3 Information exchanges between the MPS 201 and MPCS 202 (LinkL-3). L-3 Source Mine Planning System (MPS) Destination Mine PictureCompilation System (MPCS) L-3.1 Information to MPC Manager. L-3.1.1Information about managing MPC instances. L-3.2 Information to MPCinstances L-3.2.1 Information about Task plans of the entities. SourceMine Picture Compilation System (MPCS) Destination Mine Planning System(MPS) L-3.3 Information to Mine Planner. L-3.3.1 Information about theMPCS configuration. L-3-3.2 Information from the Equipment Model.L-3.3.3 Information from the Out-of-Ground Model. L-3.3.4 Informationfrom the In-Ground Model. L-3.4 Information to Job Planner. L-3-4.1Information from the Equipment Model. L-3.4.2 Information from theOut-of-Ground Model. L-3.4.3 Information from the In-Ground Model. L-3.5Information to Task Planner. L-3-5.1 Information from the EquipmentModel. L-3.5.2 Information from the Out-of-Ground Model. L-3.5.3Information from the In-Ground Model.

1.3.2. Link L-4

Information exchanges between the MPS 201 and the MCS 203 occur overLink L-4 and are shown in Table 4. The location of this link isillustrated in FIG. 2.

TABLE 4 Information exchanges between the MPS 201 and MCS 203 (LinkL-4). L-4 Source Mine Planning System (MPS) Destination Mine ControlSystem (MCS) L-4.1 Information to xIC Manager. L-4.1.1 Information aboutxIC configuration. L-4.2 Information to xIC Instances. L-4.2.1Information about a Task Plan. Source Mine Control System (MCS)Destination Mine Planning System (MPS) L-4.3 Information to MinePlanner. L-4.4 Information to Job Planner. L-4.5 Information to TaskPlanner. L-4.5.1 Information about a Task Plan.

1.3.3. Link L-5

Information exchanges between the MPCS 202 and the MCS 203 occur throughLink L-5 and are shown in Table 5. The location of this link isillustrated in FIG. 2.

TABLE 5 Information exchanges between the MPCS 202 and MCS 203 (LinkL-5). L-5 Source Mine Picture Compilation System (MPCS) Destination MineControl System (MCS) L-5.1 Information to xIC Manager. L-5.1.1Information about MPC instances. L-5.2 Information to xIC Instances.L-5.2.1 Information from the Equipment Model. L-5.2.2 Information fromIn-Ground Model. L-5.2.3 Information from the Out-of-Ground model.Source Mine Control System (MCS) Destination Mine Picture CompilationSystem (MPCS) L-5.3 Information to MPC Manager. L-5.3.1 Informationabout MCS configuration. L-5.4 Information to MPC instances. L-5.4.1Information about the Trajectory plans of entities. L-5.4.2 Informationabout the status of Tasks.

1.3.4. MAS System Operation

Consideration is now given to the system operation and to aspects of theoperation of the MAS 101, including to the system states during start-upand execution, as well as key information sequences during operation.The functional modules of the MAS 101 are shown in more detail in FIGS.3 to 6.

The order of key operations within the MAS 101 is:

1. Create an island of automation (IoA) and its associated islandcontroller 602, xIC. The creation of islands of automation may be amanual process, an automatic process or a combination of a manual andautomatic process. A manual process may involve an operator at a userinterface to the MAS 101 defining the IoA boundaries. The operator mayhave the assistance of the MPCS 202 in performing this role. Forexample, an operator may identify mining locations, roads, processingplants etc as IoAs. Automatically created IoAs may be the boundaries ofa specific mining sites in which equipment must move.2. Create a Job Planner 302 from the Mine Planner 301. This could beprovided by either a human operator 102 or automatically generated bythe Mine Planner 301. The human operator 102 may again use a userinterface and knowledge of the capabilities of available equipment toformulate a job plan. A plan may be created for a days activities andother plans may be created for longer term activities. Information fromthe MPCS 202 may be used to establish jobs, for example to plan when tomine in certain locations. Some plans may be automatically generated.For example if a spillage is detected, a plan may be automaticallycreated to assign the required clearing equipment to the location of thespillage or if a drill hole is detected as having partially collapsed, aplan for drill unit to redrill the hole formed. The plan may be formedas a ‘recommendation’ for a human operator, to either approve, reject orapprove in modified form or may be implemented automatically, subject toan ability for operator to override the plan before or after it hascommenced.3. Create a Task Planner 303 from the Job Planner 302 for each entityidentified in the job plan. Again, individual tasks may be createdeither manually or automatically. Generally, at the lower level tasksthe amount of automation may be increased. For some tasks the mineautomation system may leave the creation of sub-tasks to anotherautonomous control unit, for example the autonomous control unit of anindividual piece of equipment.4. The Task Planner 303 communicates plans for the entity to the toplevel in the xIC hierarchy 610, which passes the command down to the xIC602 holding the entity at that time.5. The entities execute the appropriate tasks. This may necessitatetransitioning between IoAs, requesting maintenance and executing themining operations.6. On completion of the task, the Task Planner 303 returns its status tothe Job Planner 302. The job plan is terminated when all entities in thejob have completed their tasks.7. The IoA may be deleted.

These sequences are described in more detail later in thisspecification.

The top level state diagram 700 for the MAS 101 is shown in FIG. 7,illustrating the operating states and transitions 705 between them. Whenexecuted, the MAS 101 enters an initialisation state 701 where the keyinfrastructure is configured and launched. When successfullyinitialised, the MAS 101 enters an idle state 702 where it awaitscommands from an operator. From this point, it will either run 703, orshutdown 704. If given the shutdown command, the underlyinginfrastructure for the MAS 101 is terminated. If run, the MAS 101launches the appropriate elements.

The state diagram for the Run_MAS state 703 is illustrated in FIG. 8,and dependencies between MAS subsystems are reflected in the statetransitions. Upon entry 802 the system passes through an initialisationand running state for each component sequentially. MPCS initialisation804 is followed by the running of the MPCS 806 until the MCS isinitialised 808. The MPCS and MCS run state 810 leads to theinitialisation of the MPS 812. With all three MAS 101 functionalmodules, MPS 201, MPCS 202, MCS 203 initialised, the system enters theMAS run state 814.

Any errors cause the system to revert to an error state, where it willattempt to resolve the problem and continue. In the case of an error inthe MPCS initialisation state 804 the system reverts to the MPCSinitialisation error state 816. In the case of an error in the MPCS runstate 806 the system reverts to the MPCS run error state 818. In thecase of an error in the MCS initialisation state 808 the system revertsto the MCS initialisation error state 820. In the case of an error inthe MPCS and MCS run state 810 the system reverts to the MPCS and MCSrun error state 822. In the case of an error in the MPS initialisationstate 812 the system reverts to the MPS initialisation error state 826.

In the case of an error in the MPCS and MCS run state 810 the systemreverts to the MPCS and MCS run error state 822. In this case the MCSwill shut down 824, and the system will attempt to resolve the problemby returning to the MPCS run state 806.

In the case of an error in the MAS run state 814 the system reverts tothe MAS run error state 828. In this case the MPS will shut down 830,and the system will attempt to resolve the problem by returning to theMPCS and MCS run state 810. If this is not possible, the system shutsdown the relevant component, MCS 824 or MPS 830, and continues withreduced functionality until it is fixed, or exits with an error 834after shutting down MPCS 832 if the error cannot be resolved.

When normal shutdown commands are issued, the system terminates each ofthe sub-systems in turn, MPS 830, MCS 824 and MPCS 832, and then exitscleanly 836.

1.3.5 Systems Operating within the Mine

Various autonomous systems may be operated within a mine, and theseelements interface with the MAS 101. Each of these systems will normallyrequire a mine picture compilation (MPC) plug-in 405 for fusing theirlocally generated information into a global model as described belowwith reference to FIG. 4. Mobile entities also will normally require aplug-in 606 for an island controller 602 as described below withreference to FIG. 6, providing an appropriate motion model fortrajectory planning.

Drill Automation—Auto Drilling/Rock Recognition: Drill automation may beemployed to provide information on geological and geophysical rockproperties on the bench at the point where a blast hole is drilled.

Drill Automation—Auto Tramming: An auto tramming sub-system for drillautomation may be employed to effect automatic tramming and positioningof the drill over required hole locations specified in a drill pattern.

Haul Truck Automation: A haul truck automation system may consist of anumber of haul vehicles capable of moving from point to point in themine according to a schedule, and able to dock at a loader or shovel andto dump at the plant or waste area.

Face inspection: Automated face inspection may employ sensors to acquirerelevant information at a current mining face.

Real-time Assay: Information on ore grades may be obtained autonomouslyfrom real-time or near real-time periodic chemical assays performed inthe process plant.

Shovel automation: Shovel automation aims to acquire information onwhere excavation occurs and on what is being excavated at any giventime. The information may be exploited to optimise and control thematerial excavation and loading process.

1.4. Mine Planning System

The MPS 201 is responsible for planning and scheduling operations withina mine. This includes short, medium and long term planning functions,and the plans within the MPS 201 may be generated either automaticallyor via human operators. For example, production targets in a mine mayspecify the quantity and quality of material that must be shipped on amonthly, weekly, and daily schedule. Given these targets, operationspersonnel along with mine engineers and geologists determine thesequence of blocks to mine (this is known as open pit scheduling) andthe allocation of resources including mine personnel, haul trucks,shovels, drills, etc. Above this may be longer term plans spanning forexample periods of 3 months, 2 years and 5 years. The longer term plansmay account for factors like long-term economic forecasting andestimated mine pit total capacity.

The MPS 201 interacts with both the MPCS 202 and the MCS 203 using theinformation dissemination links L-3 and L-4 shown in FIG. 2. Real-timeestimates of the mine provided by the MPCS 202 is the underlying modelused by the Mine Planning Systems 201 for the generation and schedulingof plans. These plans are then executed using the MCS 203 at thescheduled time.

The internal structure of the MPS 201 is illustrated in FIG. 3. Thiscomprises a hierarchal planning system with three levels identified:

1. A Mine Plan is defined as the set of all jobs required to perform alloperations in the mine, including the scheduling of equipment and/orpersonnel (also referred to as “entity or “entities”) to these jobs.

2. A Job Plan is a collection of one or more discrete tasks, which mayrequire a set of either homogeneous or heterogeneous entities. The tasksare usually grouped to achieve a common goal.

3. A Task Plan is a set of discrete actions to be carried out by aspecific entity.

The Mine Planner 301 is the highest level element in the planninghierarchy and is created when the MPS 201 is launched. The Mine Planner301 performs planning operations at a strategic level across the mine.

The Mine Planner 301 uses the model of the mine created by the MPCS 202to generate plans. Information from the model that may be used mayinclude:

-   -   The geometry of the mine, which may be used for example to        generate a dozing plan to create a road or smooth an existing        road to the requirements of a vehicle required for carrying        material;    -   Geological information, which may be used to indicate where to        mine.

The Mine Planner 301 generates the plans according to a defined set ofconstraints. These constraints are input to the system by humanoperators 102, who also have oversight of any plans that are generated.The operators 102 can also modify and delete MPS 201 generated plans,and add their own. Examples of constraints that may be input include:

-   -   Timing constraints, for example when one hole in drill hole plan        must be drilled before another;    -   Seasonal constraints, for example when certain jobs can only be        completed, or only reliably or efficiently completed during        certain times of the year;    -   Product characteristic constraints, for example where the        material output from a mine should be pre-mixed so as to result        in certain ore blends;    -   Equipment limitations, for example the capacity of equipment to        carry material, movement constraints of a vehicle and the amount        of equipment available to be used.

The scope of operations at this level includes planning future areas ofexcavation over discrete time horizons as well as planning forinfrastructure work. Examples of the latter include creating plans forthe construction and maintenance of roads, including regular watering,grading and inspection. When events occur that require unscheduled plansto be created, the MPS 201 can dynamically reschedule priorities andexisting plans to accommodate the required actions.

The Mine Planner 301 transforms the strategic plans for the mine into aseries of jobs that can be executed by specific entities. These jobplans are executed by creating a Job Planner 302 at the next level inthe planning hierarchy.

A functional job plan of the Job Planner 302 is created by the MinePlanner 301 for every defined job. A job plan consists of a set ofseparate tasks, which may require multiple heterogeneous or homogeneousentities to complete. Once created, a job plan exists until the job iseither completed or deleted. Operators 102 have authority to query,modify or delete job plans as appropriate. Multiple job plans may runsimultaneously

The MPS 201 supports both static and dynamic allocation of entities totasks. Static allocation refers to the case where a specific entity ispre-allocated to a specific task by a user and the entity must performthat task. Dynamic allocation refers to online rescheduling whereby aspecific entity is allocated a specific task.

One high-level job planner may be a Production Planner (PP). The PPreceives as input from the mine planner 301 a medium-term plan andgenerates jobs that can satisfy it. It associates a location and hencean IoA with each job, but not a particular vehicle that will execute it.Each generated job is passed on to a lower level job planner. Forexample, the PP may generate the four jobs for completion at specificlocations, which may be (specified in the form job_name(Location (Loc)where job is to be completed): graderoad(Loc), pushtopsoil(Loc),pickuptopsoil(Loc), and createwaststockpile(Loc). At any time, the jobsgenerated are those that can be executed concurrently and/orsimultaneously.

The PP must make decisions that are in compliance with the medium-termplan. A block schedule as determined in the medium-term plan andspecifying the current pit shell as well as the next pit shell to bemined may be needed from the mine planner 301 for the determination ofthe sequence of blocks to mine. Knowledge of this schedule can be usedby the PP to make rational decisions about where to construct new roadsand access ramps for current and future operations. Lastly, a geometricmap of the pit is a necessary input used in deciding on road/rampconstruction for bench access.

The Job Planner 302 creates a separate Task Planner 303 instance foreach entity defined in a job plan. If an entity type is known, but aspecific entity of that type not yet allocated, the Job Planner 302waits until a specific entity becomes available before launching thattask plan. The allocation of specific entities to a task is handled by ascheduling element within the Mine Planner 301. When all task plans in ajob are completed, the instance of the Job Planner 302 terminates andreturns.

Each job generated by the Production Planner is passed to a lower-leveljob planner responsible for further refining it into a collection oftasks that can satisfy the job (depending on the level of generalitythat the PP operates, there may also be intermediate jobs byintermediate level job planners). Each task specifies a location and avehicle as necessary. Tasks are selected to allow for concurrent and/orsimultaneous execution. Each task is passed on to a Task Planner forfurther processing. In order for a job planner to create a task plan, itrequires information about the availability of equipment, i.e., thetotal number of trucks, excavators, dozers, shovels, and gradersavailable, as well as information about current equipment assignments,utilization, and maintenance schedules. Such information about the minevehicles should be readily accessible via the Mine Picture CompilationSystem's Equipment Model.

For example, arising from the four jobs graderoad(Loc),pushtopsoil(Loc), pickuptopsoil(Loc), and createwaststockpile(Loc), thenthe following two tasks (amongst other tasks) may be created:pickuptopsoil(Loc; Vehicle), which takes two parameters which are thelocation to be processed and the vehicle that will perform the task; andload(Loc, Truck), which schedules a particular truck for loading at anexcavation island.

Generally, each JP is responsible for each of the different types ofoperations that take place in a mine. For example, one job planner couldbe used for scheduling drilling and blasting operations and another forscheduling excavation jobs.

An instance of a Task Planner 303 is created by a Job Planner 302 forevery entity in a job plan. It communicates directly with the MCS 203 toexecute the plans on the relevant entities. The task plan may includethe following information:

-   -   The target position for the entity;    -   A set of discrete tasks to be carried out; and    -   Temporal schedule for carrying out the task plan.

For example, a task planner may receive as input from a job planner thevehicle task pickuptopsoil(Loc; Vehicle) and generate a schedule ofactions that would satisfy it. This schedule is passed on to the MineControl System for execution. For example, if the Vehicle allocated bythe job planner to the task pickuptopsoil(Loc; Vehicle) was truck 10 andthe top soil was at location A, so that the task is pickuptopsoil(locA;truck10) an example of a sequence of actions may be navigate(locD, locB,truck10), navigate(locB, locA, truck10), service(excavator1, truck10).This schedule means that the truck will have to move from its currentlocation locD to locA via road locB and service the excavator there.What the truck does after loading would be specified by parsing anothertask generated by a job planner as necessary. In the above example,subscripts denote individual locations and vehicles.

In order to generate a task plan for each vehicle, the topologicalrepresentation of the mine, as created by the MCPS by fusing sensordata, is considered. One way in which the topological representation maybe considered is as a graph. FIG. 19 shows an example of representing amine using a graph. In the graph, each vertex represents an Island ofAutomation. Edges between vertices shows the connectivity between IoAs.A vehicle can travel from one vertex to another if an edge connectingthe two exists. The graph can be updated online such that if anunforeseen event requires the closure of a road, edges connecting to thecorresponding vertex can be removed and not taken into account ingenerating schedules.

In addition, each edge can be marked with a weight (not shown in FIG.19). This weight can be a function of many factors including the numberof vehicles scheduled to travel between two vertices, the steepness of aroad, the length of a road, the properties of the vehicles scheduled tooperate in an IoA (eg. fully loaded truck, empty truck, light vehicle)and possibly others relevant to creating the best schedules that conformto the plan and ensure the safe operation of the mine. Some edges mayhave infinite weights denoting that even though a particular IoA isfully operational, it has reached maximum capacity. For example, safetyrules may dictate that no more than 4 vehicles can share a road at thesame time. As a result, if 4 vehicles have already been scheduled tonavigate a particular road, an alternative path must be generated for a5th vehicle.

Using the graph shown in FIG. 19, a schedule could be generated for ahaul truck assigned the variable name truck01 currently servicingexcavator ex₀₂ at IoA mining₀₂. The job may dictate that the truck mustunload at the high grade stockpile shg₀₁. A schedule consisting ofactions for this haul truck would be:

-   -   service(ex₀₂; mining₀₂)    -   navigate(mining₀₂; ramp₀₂)    -   navigate(ramp₀₂; ramp₀₁)    -   navigate(ramp₀₁; rd₀₁)    -   navigate(rd₀₁; rd₀₄)    -   navigate(rd₀₄; rd₀₅)    -   navigate(rd₀₅; rd₀₆)    -   navigate(rd₀₆; rd₀₇)    -   navigate(rd₀₇; ramp₀₆)    -   navigate(ramp₀₆; shg₀₁)    -   unload(shg₀₁)        This schedule is communicated to the mine control system MCS for        implementation, which will return status information.        After unloading at the high grade stockpile, the haul truck        becomes available for another task which could be servicing the        same excavator, another excavator, or going to the Fuelling and        Maintenance hub fm₀₁.

1.4.1. Link L-6

Information exchanges between the Mine Planner 301 and the Job Planner302 occur through Link L-6 and are shown in Table 6. The location ofthis link is illustrated in FIG. 3. All Job Planners 302 will be createdby the Mine Planner 301.

TABLE 6 Information exchanges between the Mine Planner 301 and JobPlanner 302 (Link L-6). L-6 Source Mine Planner Destination Job PlannerL-6.1 Information about Job Plans Source Job Planner Destination MinePlanner L-6.2 Information about Job Plans.

1.4.2. Link L-7

Information exchanges between the Job Planner 302 and the Task Planner303 occur through Link L-7 and are shown in Table 7. The location ofthis link is illustrated in FIG. 3. All the Task Planners 303 will becreated by the Job Planner 302. A job plan may contain one or more taskplans. A Task Planner 303 will exist for each entity operating in themine.

TABLE 7 Information exchanges between the Job Planner 302 and TaskPlanner 303 (Link L-7). L-7 Source Job Planner Destination Task PlannerL-7.1 Information about the task plans of entities. Source Task PlannerDestination Job Planner L-7.2 Information about task plans of entities.

1.5. Mine Picture Compilation System

The MPCS 202 is illustrated in FIGS. 4 and 5 and it functions tointegrate information from a variety of spatial, spectral and geologicalsensors (not shown) into a single common operating picture of the mine.This integration may be performed in real time based on information fromthe various sensors. The specific MPC instances described below fuse thesensor data and communicate the fused data in the hierarchy. The word“picture” is not limited to a visual image, but refers more broadly to amulti-dimensional data representation or characterisation of the mine.The data may include image data. The MPCS 202 operates at many scalesand resolutions, integrating information from wide area sensors on theground or in the air, with information from local sensors on vehiclesand other platforms. In general, sensors are used in conjunction with aspecific MPC instance. However, in some arrangements wide-area data maybe partitioned and partitioned subsets may be associated with differentMPC instances.

The MPCS 202 represents diverse types of information in a common formand it has two key elements (as shown in FIG. 4):

1. a single MPC Manager 401; and

2. MPC fusion Instances 402, including (as shown in FIG. 4) a single“parent” MPC 403 and two “child” MPC's 404 linked to the parent 403 vialink L-9.

The MPC instances 402 form a hierarchy 410. Although not shown in FIG.4, the MPC instances 402 may in appropriate situations be interconnectedin any desired parent, child, etc hierarchy 410, including, for example,one having at least one “grandchild” MPC (not shown in FIG. 4) linked toone or another child MPC 404. In some embodiments there is a one-to-onerelationship between the hierarchy 410 of MPC instances and thehierarchy of xIC's, with the structure of the xIC's dictating thestructure of MPC instances.

Each MPC instance 402 has plug-ins 405 specific to the equipment andhuman operators to which it is connected. The required bandwidth of thecommunication channels of the MPC instances 402 in the lower level ofthe hierarchy will be determined by the nature of plug-ins 405interfaced to the MPC instance 402.

MPC information is made accessible through the use of model plug-ins405. Model plug-ins 405 are software elements that “plug-in” to thesystem such that they have complete access to the internal MPCinformation. The fusion system is then constructed using the generic MPCinstance 402 as a framework, and by writing specific model plug-ins 405that can update the underlying MPC representation for each differentinformation type. The updating by a model plug-in 405 may occur, forexample, on receipt of new sensor data or on receipt of information thatindicates that equipment has changed location. The updating may occur inreal-time or on a scheduled basis, or when another update triggeroccurs. This architecture permits the MPCS 202 to be extended to use newinformation types if or when they become available without the need torewrite any existing elements of the system.

Also, each MPC instance 402 may have any number of these plug-ins 405,each of which can perform a different task. MPC plug-ins 405 willtypically include the following functions:

-   -   Read MPC state information and output to user;    -   Read MPC state information, transform to alternate format and        output;    -   Update MPC models with new information about entity pose        (position and orientation);    -   Update MPC models with new information from the rock recognition        system;    -   Update MPC models with new information from the face inspection        system;    -   Update MPC models with new information from third party systems.

The MPC Manager 401 is the MPCS component created when the systemstarts. Its function is solely to manage the network of hierarchical MPCfusion Instances 402 which may be distributed spatially throughout themine and a remote operations centre, ROC. It does not maintain the fusedinformation and it does not perform fusion operations.

The key responsibilities of the MPC manager 401 are to create, delete,configure and manage the network of MPC instances 402. These Instances402 are dynamically created and managed based on information sent to theMPC manager 401.

1.5.1. Link L-8

Information exchanges between the MPC Manager 401 and the MPC instancehierarchy 410 (Parent 403 and Child 404 modules) occur through Link L-8and are shown in Table 8. The location of this link is illustrated inFIG. 4. The MPC Manager 401 is created during the start-up operation ofthe system and creates MPC instances 402 whenever necessary.

The MPC Manager 401 is responsible for creating, updating and deletingof MPC instances 402. Each MPC instance 402 will be allocated with aspecific address or index that is used to identify the MPC instance 402in the MPC hierarchy 410.

TABLE 8 Information exchanges between MPC Manager 401 and MPC instance402 (Link L-8). L-8 Source Mine Picture Compilation Manager DestinationMine Picture Compilation (Parent Module and Child modules) L-8.1Information about creating/updating and deleting MPC instances. SourceMine Picture Compilation (Parent Module and Child modules) DestinationMine Picture Compilation Manager L-8.2 Information about the status ofMPC instances.

The MPC instances 402 will normally be designed to be capable ofsupporting hierarchical topologies 410. Each MPC instance 402 will havethe same properties and algorithms as its parent MPC instance 403. ChildMPC instances 404 may operate on any subset of information availablefrom their parent 403. When operating on a subset of the totalinformation state, the requirements for bandwidth and informationprocessing power at the child MPC instance 404 are reduced accordingly.

1.5.2. Link L-9

Information exchanges between the MPC Parent 403 and an MPC Child 404occur through Link L-9 and are shown in Table 9. The location of thislink is illustrated in FIG. 4. Both MPC Parent 403 and MPC Child 404 arecreated by the MPC Manager 401.

An MPC Child 404 can extract, copy or update a region of the MPCS 202representation from its parent. Both the MPC Parent 403 and Child 404instances may be modified or deleted by the MPC Manager 401.

TABLE 9 Information exchanges between MPC Parent 403 and MPC Child 404(Link L-9). L-9 Source Mine Picture Compilation (Parent) DestinationMine Picture Compilation (Child) L-9.1 MPC representations. Source MinePicture Compilation (Child) Destination Mine Picture Compilation(Parent) L-9.2 MPC representations.

Referring to FIG. 5, the MPC instances 402 comprise three primary modelsresponsible for monitoring the properties of the mine. The in-groundmodel unit 501 maintains a multi-scale probabilistic representation ofthe geology and geometry of the mine. The out-of-ground model unit 502maintains a representation of the material in process and stockpiles.The equipment model unit 503 maintains a representation of equipment.

Methods and systems for generating a model of an environment using anin-ground model, an out-of-ground model and an equipment model aredescribed in co-assigned application titled “Method and system forexploiting information form heterogeneous sources”, filed as PCTapplication PCT/AU2009/000265 claiming priority from an Australianprovisional application filed on 4 Mar. 2008, which is incorporatedherein by reference in its entirety.

The in-ground model unit 501 is responsible for maintaining and updatinga multi-scale probabilistic representation of the geometry and geologyof the in-ground material. Included in this model are geometricproperties (walls, benches, etc), hole positions and drill patterns,geological information such as disposition of shale, Banded IronFormation (BIF) and iron ore zones, chemical composition, and mechanicalproperties of these zones including rock factors and hardness.

The in-ground model unit 501 integrates information from sources such assurvey 504, rock recognition 505, face inspection 506, chemical assaysand exploration holes to better model and predict the geometry andgeology of material in the ground. This information is spatiallyheterogeneous at many scales and is necessarily uncertain.

The data fusion engines 507 operate as applications on the common database. The output of the combined fusion operation is identified as thecommon operating picture (COP) 508, a best estimate of all spatial andgeological properties based on the combined evidence from all sources ofinformation. Different fusion algorithms and methods are employed fordifferent types of estimate. For example, best spatial estimates forgeological structures may require the use of a Gaussian Process modelwhich describes spatial correlations in data, best surface models can beobtained from irregular spatial tessellations, and geological classinformation from a discrete classifier. Using a client structure for thedata fusion allows different data fusion algorithms to be incorporatedinto the system.

The COP 508 contains the best estimate of quantitative geometric,geological and geophysical properties, qualified with statisticalconfidence bounds. This information can be accessed through specificdata requests from any other service provider in the mine. Data requestsmay originate from automated machines, such as drill rigs (that requireinformation for purposes of control and optimal operation), individualdecision makers, such as planners, who require this information to planmining operations, or display units at local or remote sites. Differenttypes of request need to be supported including those in restrictedspatial areas or those for which data is required in real ornear-real-time.

The out-of-ground model unit 502 reconciles material (as it isexcavated, transported and stockpiled) with in-ground resource estimates509 in the in-ground to lumped-mass reconciliation unit 510. Theout-of-ground model unit 502 fuses information from the in-ground modelunit 501 with data (from for example, shovel sensors 511) to obtainestimates of quantity and grade during material removal from the face.Fusion is performed by the Lumped-mass Fusion Engine 512. Thisinformation is propagated during haulage and reconciled withobservations made by material flow measurement and assay in the plant,and further reconciled with post-plant stockpile surveys. Theout-of-ground model unit 502 generates a lumped mass model 513 withassociated geophysical and chemical attributes. The mass model 513 isideally tied to the point of excavation for use in post-miningrefinement of the resource model. The mass model 513 can, on demand,estimate the location and grade of all available stock in the mine.Information about unexcavated, broken stock is utilised by the in-groundmodel unit 501.

The out-of-ground model unit 502 describes flow from in-ground tostockpile reclaiming. Fundamentally, the model 513 must conserve massand attributes as material flows through the system from bench to train.Each step in the process involves measurements which identify local flowcharacteristics. These measurements need to be fused to reconcilematerial conservation. Current estimates must be made available formaterial management and scheduling.

The equipment model unit 503 maintains and updates information 514related to equipment location and status. Much of this information ismade available through existing dispatch systems for trucks and shovels.The equipment model 515 provides an interface through which informationcan be exchanged between these existing systems and the MPC system 202and in particular to enable the out-of-ground model unit 502 toreconcile material models at the bench with material flows through theplant. The equipment model 515 receives equipment position, dispositionand status.

1.6. Mine Control System

Reference is now made to the Mine Control System, (MCS) 203, asillustrated in FIG. 6. The MCS 203 functions within any required numberof localised zones (referred to herein as “islands of autonomy”,“islands of automation” or “IoA”) that have operation-definedgeographical boundaries within a defined mine region and, associatedwith the islands of autonomy, island controllers 602 (“xIC's” or “xICInstances”) governed by a single xIC Manager 603.

The xIC Manager 603 is created when the MCS 203 starts and its functionis solely to manage the network of xIC Instances 602 which may bespatially distributed throughout the mine and ROC. It does not itselfperform any control functions within the islands of automation.

The key responsibilities of the xIC Manager 603 are to create, delete,configure and manage the network 610 of xIC instances 602. Theseinstances are dynamically created and managed based on information sentto the xIC Manager 603.

The xIC Instances 602 provide a common control system for all IoAs. EachxIC Instance 602 can be identical to all others and all are created andmanaged by the xIC Manager 603. As shown in FIG. 6, the xIC's 602 in thenetwork 610 are configured in a hierarchy that is determined by thespatial location of the IoAs within the mine. The top of the hierarchycorresponds to the IoA encapsulating the entire mine, and the systemthen distributes recursively with the next layers respectively, with“parent” 604 and linked “child” 605 xIC's as shown in FIG. 6. There is a1:1 mapping of xIC Instances 602 and islands of automation and, if achild IoA is created inside a functioning IoA, the parent xIC 604 willhave full control over the child IoA. Similarly, if a grandchild IoA iscreated inside a functioning child IoA, the child xIC 605 will have fullcontrol over the grandchild IoA.

Control by the MCS 203 is hierarchical and thus the control tasks mayfall into higher-level tasks and lower-level tasks. A parent xIC 604 maysupervise the control tasks of a child xIC 605. An xIC may direct orsupervise a control system of an autonomous entity operating within anIsland of Automation. Thus for example, an autonomous vehicle mayreceive the higher-level command “Move to location x”. The local controlof the autonomous vehicle or group of autonomous vehicles may then beresponsible for controlling the systems and actuators of the vehicle inorder to move the vehicle(s) to the specified location. In other words,the MAS 200, through the MCS 203 is performing the operations of amanagement party for autonomous operations within the highest level IoA,the management party performing functions that include the job or tasklevel control of a lower level autonomous system, which will manage itsown tasks in response to the receipt of a job or higher level taskcommand.

1.6.1. Link L-10

Information exchanges between the xIC Manager 603 and the xIC Instances602 occur through Link L-10 and are shown in Table 10. The location ofthis link is illustrated in FIG. 6. The xIC Manager 603 is created whenthe MCS 203 is executed. The xIC Manager 603 is responsible forcreating, updating and deleting xIC Instances 602. The xIC Instances 602are responsible for controlling activities within a specific IoA.

TABLE 10 Information exchanges between xIC Manager 603 and xIC Instance602 (Link L-10). L-10 Source xIC Manager Destination xIC Instances(Parent Module and the Child Modules) L-10.1 Information aboutcreating/updating and deleting of xIC Instances. Source xIC Instances(Parent Module and the Child Modules) Destination xIC Manager L-10.2Information about the status of xIC Instances.

1.6.2. Link L-11

Information exchanges between the xIC Parent 604 and the xIC Child 605Instances occur through Link L-11 and are shown in Table 11. Thelocation of this link is illustrated in FIG. 6. Both the xIC Parent 604and xIC Child 605 are created by the xIC Manager 603.

TABLE 11 Information exchanges between xIC Parent 604 and xIC Child 605(Link L-11). L-11 Source Island Controller (xIC - Parent) DestinationIsland Controller (xIC - Child) L-11.1 Information about the task plansof entities. L-11.2 Information about registration and deregistration ofentities from an Island of Automation. Destination Island Controller(xIC - Child) Source Island Controller (xIC - Parent) L-11.3 Informationabout task plans of entities. L-11.4 Information about registration andderegistration of entities from an Island of Automation.

Although the core xIC Instances are all identical, each IoA can operatewith different control rules, priorities or entities through the use ofplug-ins. Each xIC Instance 602 has two distinct types of plug-ins, asdescribed below, a so-called “behaviour plug-in” 607 and an “entitymodel plug-in” 606.

Every entity entering an IoA is first registered in the associated xIC(eg 605), the registration being coordinated by the parent xIC 604 asdescribed in detail later in this specification.

Each xIC 602 interacts with at least one MPC instance 402 for each IoA.This is needed to obtain information from the above described in-groundmodel unit 501, out-of-ground model unit 502 and equipment model unit503 to execute the tasks within the IoA.

The behaviour plug-in 607 specifies IoA-specific features, which mayinclude the equipment that can operate in the IoA, operations which maybe carried out in the IoA, type of the IoA, information aboutunauthorised entities and actions for the IoA and rules and regulationsfor performing tasks in the IoA.

The entity model plug-ins 606 serve two main purposes:

-   1. Being specific to a particular type of entity, a given plug-in    606 enables the xIC 602 to generate appropriate controls for the    relevant entity.-   2. A given plug-in 606 specifies the communication interface to the    entity.

Each xIC 602 requires the appropriate entity model plug-in 606 for eachentity in the IoA, and there is no limit to the number of plug-ins thatcan be connected at any one time.

The use of the entity model plug-in 606 to communicate to the entitymeans that the key control interface standard is between the plug-in 606and the xIC 602. Separate standards may then be generated forcommunication to each different class of entity. The plug-in interfaceensures that there is a single standard that can be common across alldifferent classes of entities. Thus, although the informationcommunicated between a plug-in and a drill may differ from that betweena plug-in and a haul truck, the interface between the xIC 602 and bothplug-ins is common.

Consideration is now given to the execution of control within the IoAs.

The hierarchy 610 of the control system 203 is deployed with softwareelements assigned to spatial regions of the mine, known as zones orislands of operation. The control system 203 is designed specifically toprovide the flexibility to operate mixes of both human systems andautonomous systems safely within the same mine or mine region, and thefollowing contains a description of the core functions within the MCS203.

An operator 102 uses the MAS interface to define a new IoA, which thensends this information to the xIC Manager 603. The operator 102 isrequired to specify parameters such as:

-   -   Island boundaries;    -   Transition zones;    -   An MPC instance 402 to connect to;    -   A behaviour plug in 607; and    -   A physical deployment location.

Once all required parameters are set, the xIC Manager 603 creates thexIC Instance 602 according to the specifications given. The new xICInstance 602 initiates the process of registering itself to the parent604 in the hierarchy 610, and awaits confirmation. The parent 604 willthen transition the control of all entities within the boundaries of thenew island to the new xIC controller. The xIC 602 registers its MPCplug-in 405 with the specified MPC instance 402, which then confirms itsstatus to the xIC Manager 603. The xIC Manager 603 alerts the MPCS 202that the island exists and is active and returns the status to theoperator 102.

The process of varying the geographic boundaries of an IoA is similar tothe process of creating a new IoA. The variation may be instigated atvarious points in the system. For example, an operator may use the MASinterface to specify that a change is required. The operator specifiesthe revised island boundaries and, if necessary, may define one or moretransition zones for the revised island.

In some arrangements there may be an automated variation of islandboundaries. For example, the size of a bench may be automaticallyincreased or decreased depending on a calculated drill pattern. Inanother example, the geographic boundaries of an excavation zone may beautomatically increased as the excavation proceeds.

When the island boundaries change, the system may check to ensure thatentities within the island before the change remain within the islandafter the boundary change. If an entity falls outside the island as aresult of the boundary change, then control of the entity is transferredto another IoA. For example, if the boundary of xIC instance 605 isvaried, control of an entity formerly within xIC 605 may be transferredto the parent xIC 604 in the hierarchy 610.

Similarly, if a change to a boundary means that an entity will fallwithin the boundary, then control of the entity is transferred to thexIC of the changed IoA. This transfer may require handshaking betweenthe xIC of the varied island and the xIC of its parent.

An alternative approach to varying the boundary of an existing island isto delete the island and then to create a new island with the redefinedgeographical boundary.

If an IoA is to be deleted, an operator 102 sends the command to the xICManager 603, which then sends the deletion command to the relevant xICinstance 602. The xIC Instance 602 must pass control of all entitieswithin its boundaries to its parent 604 in the hierarchy 610, thenderegister itself from that parent 604. If successful, the instancederegisters its MPC plug in 405, confirms status to the xIC Manager 603and terminates. The MPCS 102 and the operator 101 are alerted that thexIC 602 has been deleted. The stages in this sequence correspond withthose in the creation process.

2. Transitions

FIG. 9 illustrates the components involved when an entity moves from onezone to another.

Transitions from and between IoAs are performed using a pull-basedmechanism in which a receiving IoA 901 drives the request for an entity902 through the parent island 903 that then coordinates with the base904 (island currently responsible). An entity 902 is then transitionedusing a double-handshake protocol. The transition occurs at a specificport 905 within transition zones 906, 907. The process has secondarycontrol added to an entity before entry into a region and prior controlauthority is removed only once the entity has fully transitioned.

The general procedure is:

1. Find the lowest layer that encapsulates the entire region needed forthe task required. This is considered the parent IoA 903.

2. The receiver xIC 910 (at the command of the supervising parent 903)creates a space for the receipt of the entity 902 at the requisite port905.

3. Then the base xIC 912 (at the command of the supervising parent 903)will determine if the entity 902 can be freed and transferred to therequisite port 905.

4. The parent 903 will then coordinate (and if necessary disambiguate)the transition by commanding the base 904 to move the entity 902 to thetransfer port 905 and its given transition zone 907.

5. When the entity enters the transition zone 907, the registrationprocess begins. This is the first part of the handshake. This entailsthe entity 902 notifying the base xIC 912, which notifies the parent xIC914, which notifies the receiver xIC 910. During this, the entity 902 isopen to receiving forward looking operations for actions in thetransition zone 906 of the receiving xIC 910. The entity 902 thenreceives secondary control from the receiver 901. As part ofinitialization to the receiving xIC 910, the entity 902 is given thegeographic bounds, transition zone bounds, and travel path to execute asuccessful transition. Once the entity 902 has transitioned into thespace 906 of the receiving xIC 910, the deregistration process beginsfor the base xIC 912. This is completed before leaving the receiver'stransition zone 906.

The entity 902 maintains a control list through which the receiving xIC910 obtains secondary control during the transition. A safety commandtakes precedence regardless of the controller issuing it.

The control architecture has been developed to be consistent with the“lockholder” policy practised in a mine site. The addition of control isanalogous to adding a personal isolation lock. Thus, a control “lock”for a particular xIC can only be removed by that xIC. Further, tooperate in a xIC requires the control “lock” of that xIC. Control isadded and removed in the transition zones 906, 907. Thus, the receiverxIC 910 adds its control “lock” to the entity 902 while the entity is inthe base's transition zone 907. On the transfer of an entity 902 to thereceiver IoA 901 (and control to its xIC 910), then the base xIC 912will “unlock” control within the transition zone 907 of the receiver.

Referring to FIGS. 10a-10e an example is shown of a transition of anentity 902, “Entity X”, from a base xIC 912, “Base xIC B”, to a receiverxIC 910, “Receiver xIC C”, via a port 905, “Port P” as supervised by aparent xIC 914, “Parent A”.

In FIG. 10a the parent xIC 914 sets up the transition. In FIG. 10b theparent xIC 914 hands over the control from the base xIC 912 to thereceiver xIC 910 in the transition zones 906 and 907. In FIG. 10c thebase xIC 912 controls the transition of the entity 902 into thetransition zone 907. In FIG. 10d the base xIC 912 deregisters control ofthe entity 902, and the receiver xIC 910 takes over the control of theentity 902 for the receiving zone 901.

In FIG. 10e all the handshake signals required for the whole transitionprocess are shown.

The process for transition of control follows the sequence:

-   -   1. A→C: Query: Can you accept X?    -   2. C→A: Acknowledgment    -   3. A→B: Query: Can you release X?    -   4. B→A: Acknowledgment    -   5. A→B: Command: Move X to Port P        -   a. B→X: Command: trajectory for moving to P, coordinates of            transition zone in B.        -   b. X→B: Acknowledgment, status updates        -   c. X→B: Entered transition zone        -   d. B→X: Control non-exclusive, can receive future control            messages from C        -   e. X→B: Acknowledgment    -   6. B→A: Status Update: Transition ready    -   7. A→C: Command: C to send future control commands to X        -   a. C→X: Initiation to IoA C (bounds, trajectory zone, etc.),            future control trajectories in transition zone, etc.        -   b. X→C: Register entry        -   c. C→X: Acknowledgment        -   d. X→C: Acknowledgment    -   8. C→A: Status update and acknowledgment    -   9. A→B: Command: Deregister B        -   a. B→X: Deregister control        -   b. X→B: Deregistration message/acknowledgment    -   10. B→A: Acknowledgment    -   11. A→C: Deregistration acknowledgment        -   a. C→X: Authority to execute trajectories beyond the C            transition zone        -   b. X→C: Acknowledgment    -   12. C→A: Acknowledgment

The transition between islands can also be viewed as a sequence in time.

A temporal sequence for transitioning between islands is shown in FIG.10 f.

The control list on Entity X 902 for this sequence varies as X 902enters the transition zone 907, crosses the port 905, and exits thetransition zone 906. On entry of the transition zone 907, base xIC 912has primary control, and then has secondary control transitioned to thereceiver xIC 910. In this manner, the receiver xIC 910 can communicateand feed forward control before the port 905. After crossing into thereceiving IoA 901, the base xIC 912 still maintains communication so asto allow it to deregister. In addition to safety, deregistration isimportant for the base xIC 912 to free resources that were cleared andallocated to the entity's transition.

A temporal sequence for the control loss during transitioning betweenislands is shown in FIG. 10 g.

Another aspect of this architecture is that an entity 902 gets futureway-points or trajectories for its future planning before fulloperational control. Once the entity 902 has transitioned to thereceiver transition zone 906, there is no need for the base xIC 912 togive trajectories or plans.

A temporal sequence for future trajectories is shown in FIG. 10 h.

Task commands are passed from the Task Planner 308, to the top level ofthe control hierarchy 610. Two types of movements are relevant:

1. A Mining move—any control that is designed to change the geometry orvolumetric content of the mine; and

2. A Standard move—all other control.

The commands are then passed down the hierarchy 610 to the xIC Instance602 responsible for the entity 902 in question. The xIC Instance 602converts the task command into a trajectory and sends this to the entity902 for execution.

3. Example of Mine Site Operation

A much-simplified, representative example of a mine site operation isnow described for the purpose of illustrating the MAS architecture 100.However, it is to be understood that the example is given to illustratekey aspects of the MAS functionality rather than to capture all aspectsof a real mining operation. The description is provided with referenceto FIG. 11, which illustrates an open pit mine having a processing plant1102 connected by a single road 1104 to a bench 1106 and an adjacentarea 1108 where loading is undertaken. Various aspects of the mine siteoperation are described under the following sub-headings.

3.1. Planning

FIG. 12 illustrates the MPS configuration applicable to this example.Starting from the assumption that the material in the face loading area1108 is to be mined and transported to the processing plant 1102, a JobPlanner 1206 in the MPS 1202 is used to create a job plan to excavatethe required volume of material at the appropriate location. The jobplan assigns an excavator 1116, four trucks 1112 and a dozer 1114 to theprocedure. The entities are assigned permanently by an operator, but thesystem 100 could also dynamically schedule vehicles depending uponrequirements. The Job Planner 1206 then creates a Task Planner 1208 foreach entity. The Task Planners 1208 execute the plans through the MCS1304, as illustrated in FIG. 14. The Task Planners 1208 communicateplans for the respective entities to the top level in the xIC hierarchy1304, the mine controller 1314; the mine controller 1314 then passes thecommand down to each subsidiary controller: the plant controller 1316,road controller 1318, bench loading controller 1320 and face loading1308 controller. The face loading controller 1308 is subsidiary to thebench loading controller 1320. The communication links 1402 also returninformation from the MCS 1304 to the MPS 1202 relating to task plans(see Table 4).

3.2. Islands of Automation

An IoA is created for each of the geographic regions identified in FIG.11. At the highest level, the entire mine is an IoA 1110 and, within themine, the plant 1102, road 1104 and bench 1106 each become a separateIoA. Finally, a face loading IoA 1108 is created within the bench toenclose the excavator 1116 and trucks 1112 at the time of loading. ThexIC hierarchy 1302 of the MCS 1304 for this example is shown in FIG. 13.As the mining operations proceed, the geographical boundaries of theface loading island 1108 and the bench loading island 1106 may be variedto match the current location of the operations.

3.3. Controlling the IoAs

The mine IoA has a mine controller 1314. The plant IoA 1102 has a plantcontroller 1316. The road IoA 1104 has a road controller 1318. The benchloading IoA 1106 has a bench loading controller 1320. The face loadingIoA 1108 has a face loading controller 1308.

Each of the IoA controllers as shown in FIG. 13 has a behaviour plug-in(eg plug-in 1324 for the mine IC 1314) that provides parameters in theform, for example, of details of the exact control behaviours,constraints and rules within that geographic region. For example, thepriority of entities or road rules around the plant 1102 may differ fromthose at the bench 1106.

Each of the entities in the mine is registered to the island controllerfor its geographic region. Thus, these island controllers each have amodel plug-in for the vehicles (entities) they are controlling. Forexample, the face loading IoA 1108 has a model plug-in for both theexcavator 1310 and a plug-in for the truck 1312, the road IoA 1104 has atruck plug-in 1306, and the bench loading IoA 1106 has a truck plug-in1326 and a dozer plug-in 1328. As the plug-ins contain the model for anentity, a single plug-in can be used to control multiple homogeneousentities in the same island.

The key responsibilities of the xIC Manager 1322 are to create, delete,configure and manage the network of xIC instances 1302. These instancesare dynamically created and managed based on information received by thexIC Manager 1322, for example jobs or tasks received from the mineplanning system.

The deployment configuration for this system desirably has the softwarefor the island controllers running as close as practically possible tothe relevant islands. This is so that the controllers will communicatewith the entities in the islands with minimal latency and to reduce theneed for mine-wide messaging of information that is only relevant to asmall region. Example deployments are given as follows:

a) Mine IoA Controller 1314: This may run on a server at the centralprocessing facility for the mine.

b) Plant IoA Controller 1316: A processing facility may be establishedat the plant to allow the controller to be spatially located at thatsite.

c) Road IoA Controller 1318: As the road network is distributedthroughout the mine, the island controller may desirably run at thecentral processing facility.

d) Bench IoA Controller 1320: The controller for the bench may run onthe excavator 1116. This entity stays in the island whereas trucks andother vehicles are likely to transition regularly.

e) Face Loading IoA Controller 1308: The controller for the faceexcavation is conveniently run on the excavator, along with the BenchIsland Controller 1320. This will allow a permanent wired, highbandwidth communications link between the two.

3.4. Mine Picture Compilation

FIG. 15 shows the MPCS 1502 for this example. One possible deploymentconfiguration for this system will have the various MPC devices asillustrated in FIG. 15 and referred to as follows:

a) Mine MPC 1508: This MPC device is the core of the MPC hierarchy 1506and contains the global mine operating picture. It may be run at thecentral processing facility with a wired, high bandwidth connection tothe Mine Island Controller 1314. In this example, it has only a singleplug-in 1510 connected which enables systems and operators external tothe MPCS 1502 to access fused MPC information.

b) Road MPC 1512: The road MPC device extracts information for the roadareas. It may be run at the central processing facility with a wired,high bandwidth connection to the Road Island Controller 1318. Itcontains model plug-ins with the following functions:

1. Road monitoring 1514: Update the in-ground geometry model with roadsurface data from vehicles;

2. Equipment Pose 1516: Update the equipment model with vehicle poseinformation;

3. Road xIC 1518: Enable an interface to the Road Island Controller1318. This provides the island controller 1318 with access to the fusedMPC information, and allows the road MPC 1512 to access trajectoryinformation from the controller 1318.

c) Plant MPC 1520: The plant MPC device extracts information for theplant region. It may be run on a processing facility located at theplant, with a wired, high bandwidth connection to the Plant IslandController 1316. It contains model plug-ins with the followingfunctions:

1. Plant monitoring 1522: Update the out-of-ground model with real-timeassay information from the plant;

2. Equipment Pose 1524: Update the equipment model with vehicle poseinformation;

3. Plant xIC 1526: Enable an interface to the Plant Island Controller1316. This provides the island controller 1316 with access to the fusedMPC information, and allows the plant MPC 1520 to access trajectoryinformation from the controller.

d) Bench MPC 1528: The Bench MPC extracts information for the benchregion. It may be run on a processing facility on the excavator with awired, high bandwidth connection to both the Bench Loading IslandController 1320 and the Face Loading Island Controller 1308. It containsmodel plug-ins with the following functions:

1. Bench monitoring 1530: Use bucket scanning to update the in-groundand out-of-ground models as material is excavated.

2. Equipment Pose 1532: Update the equipment model with vehicle poseinformation.

3. Bench xIC 1534: Enable an interface to the Bench Loading IslandController 1320. This provides the island controller 1320 with access tothe fused MPC information, and allows the bench MPC 1528 to accesstrajectory information from the controller 1320.

4. Face Loading xIC 1536: Enable an interface to the Face Loading IslandController 1308. This provides the island controller 1308 with access tothe fused MPC information, and allows the bench MPC 1528 to accesstrajectory information from the controller 1308.

The bench 1106 and face loading 1108 islands in this example areconfigured to operate on the same MPC instance 1528, reducing the numberof MPCs running and hence the complexity of the system. However, analternative strategy would be to have an extra MPC instance for the faceloading island 1108 and accept the extra computing and complexityrequirements.

3.5. System Integration

FIG. 16 illustrates connection links between the MPCS 1502 and MCS 1304.When each of the xIC Instances is created, it registers a xIC plug-inwith an MPC instance.

The plant xIC 1316 registers the plant xIC plug-in model 1526 with theplant MPC 1520 over a link 1602. The road xIC 1318 registers the roadxIC plug-in model 1518 with the road MPC 1512 over a link 1604. Thebench loading xIC 1320 and the face loading xIC 1308 register the benchxIC plug-in model 1534 and the face loading xIC plug-in model 1536 withthe bench MPC 1520 over links 1606 and 1608 respectively.

It is through these links that the controllers receive the latest stateinformation from each MPC instance and transmits planned trajectoryinformation to each MPC instance. In this example, both the Bench 1106and Face Loading 1108 IoAs are connected to the same MPC instance 1528.As both of these island controllers are deployed on the same entity, theexcavator, both can use a common MPC instance 1528. Importantly, the MPCinstance 1528 should be deployed at the same physical location as thecontrollers 1320, 1308 and connected through a hardwired link toaccommodate both communications links 1606, 1608, as these form part ofa control loop.

FIG. 17 illustrates the control loop between the MCS 1304, entities inthe mine 1110 (including trucks 1112, a dozer 1114 and an excavator1116) and the MPCS 1502. Communications between the MPCS 1502 and MCS1304 as illustrated in FIG. 16 are summarised as a single link 1702 forclarity.

xIC entity plug-in models that communicate control information to theentities include the truck plug-ins 1306, 1326, 1312, the dozer plug-in1328 and the excavator plug-in 1310. This information is communicatedacross communication links 1706 Information from the entities is thensent to the MPC plug-ins: the road mapping plug-in 1514, the equipmentpose plug-in 1516, the road xIC plug-in 1518, the bench monitoringplug-in 1530, the equipment pose plug-in 1532, the bench xIC plug-in1534 and the face loading xIC 1536. This information is sent overcommunication links 1704 between the entities and the MPC plug-ins, andis used for fusion into the appropriate MPC model. This demonstrates thecontrol loop between the MCS 1304, entities in the mine and the MPCS1502.

FIG. 18 illustrates how all elements of the MAS 1800 in this exampleform an integrated system. The island of automation that is defined bythe whole mine site 1110 is controlled by the MAS 1800. The MAS 1800comprises the MPS 1202, the MCS 1304 and the MPCS 1502. Communicationoccurs between the MPS 1202 and the MCS over bidirectional communicationlinks 1402 as shown in FIG. 14. Communication occurs between the MPS1202 and the MPCS 1502 over bidirectional communication links 1802providing the MPCS 1502 with information about managing the MPCinstances and about task plans of the entities and providing the MPS1202 with information about the MPCS configuration and with informationfrom the in-ground model, the out-of-ground model and the equipmentmodel (see Table 3). Communication occurs between the MCS 1304 and theMPCS 1502 over communication links 1702 as described with reference toFIG. 16: the MCS 1304 receives information about the MPC instances andinformation from the equipment model, in-ground model and out-of-groundmodel; the MPCS 1502 received information about the MCS configuration,the trajectory plans of entities and the status of tasks (see Table 5).

The embodiment illustrated in the Figures and described above relates toa mining application. It will be appreciated that there are many otherfields of application relevant to integrated autonomous control,including forestry and agriculture. The automation system of FIG. 2 maybe used to control autonomous operation of equipment in variousapplications where a plurality of localised zones havingoperation-defined geographical boundaries are established within aregion.

In the mining application, the term “in-ground information” refers togeometrical, geophysical and geological information about in-groundmaterial, along with information about mining activities that haveoccurred or are to occur prior to the extraction of the material. Thein-ground or unexcavated material is material that has not beenexcavated yet. Geometrical information represents information about thelocation and the geometry of the mine, benches, etc. It also includesinformation about the location of existing or to-be-drilled holes andtheir dimensions. This constitutes a drill pattern. Furthermore,geometrical information can also have associated information relating toquantity and composition of explosives to be provided in the holes.Using the in-ground information, it is possible to estimate quantity andstocks of in-ground material. In-ground information also compriseschemical and mechanical properties of the different zones of the mine.All in-ground information is fused to form an in-ground model.

In an agricultural application the term “in ground information” mayrelate to the soil and economically useful plants or crops in a regionof interest. The in-ground model obtains, through sensing, an integratedpicture of the geometry, chemical composition, and crop health over therequired area. More generally, the term “in-ground information” fallsinto the class of “pre-extraction”, “pre-intervention” or“pre-processing” information and refers to information describing aregion at some starting reference point, or a relative startingreference point within a dynamic process subject to continualre-evaluation. The region resource may be, for example, a mine, anagricultural resource or a forestry resource that is subject tointervention or processing by the equipment referred to below. In thisbroader sense the “in-ground information” is not limited literally toinformation relating to the ground, but may, for example refer to amarine resource.

In this description a second type of information is termed“out-of-ground information”. In the mining application the“out-of-ground information” refers to information about the extracted orout-of ground material including stockpiles and material in process.This information includes, but is not limited to, geophysical, chemicaland grade of the out-of-ground material in addition to its locationwithin the mine. Using the out-of-ground information, it is possible toestimate the stocks and quantity of out-of-ground material. Theout-of-ground information is fused to form an out-of-ground model.

In an agricultural application the out-of-ground information may, forexample, describe a harvested crop. More generally, the out-of-groundinformation falls into the class of “post-extraction”, “post-processing”or “post-intervention” information that describes material extracted orharvested from the environment described by the in-ground(pre-extraction) information. In some applications the out-of-groundlabel does not related literally to the ground, but may, for example,have reference to a harvested marine resource.

The expression “equipment information” refers to information relating tothe pieces of equipment used in a resource-processing application. Theequipment is instrumental in transferring material from the in-ground orpre-processing environment to the out-of-ground or post-processingenvironment. In the context of a mining operation, for example,“equipment information” refers to information relating to the pieces ofequipment used in a mine and to its operators. The equipment informationincludes, but is not limited to, the number, the location, the status,the disposition, and the type of the piece of equipment. It alsoincludes scheduling and logistic information. All equipment informationis fused to form an equipment model.

The term “automatic” refers to a system or process that executes aspecific well-defined task that is often narrowly defined. “Automatic”implies following a set of well-defined rules and reacting in a definedway to a defined stimulus. “Automated systems” are those that have someautomatic components or properties.

The term “autonomous” refers to systems that are more complex as thesystems are able to respond to unknown stimuli and can function withouta complete knowledge of their environments. Typically, an autonomoussystem does not require human intervention to respond to at least someunpredicted changes in its environment.

The three models relating to in-ground, out-of-ground, and equipmentinformation, may be used to form an overall integrated picture for usein monitoring and exploiting an environment such as a mine. The modelsmay also be applied to the fusion of information for estimation inforestry and agriculture applications, for example the fusion ofin-ground information such as soil properties with out-of-groundinformation such as crop or harvest data. The equipment or operationunits in this example might include tractors, ploughs and otheragricultural equipment.

In a similar manner, fusion of in-ground information may also be usedfor drainage or irrigation applications. Further applications may alsoinclude the fusion of information for estimating properties of the oceanor other liquid bodies. Maritime examples include the use of thein-ground model to estimate properties such as ocean temperature andsalinity. “Out-of-ground” type estimates may relate to any marineresource including fish or minerals extracted from the ocean. In marineapplications the equipment entities may, for example, include fishingvessels, nets and submarines, and the “in-ground” model may, forexample, include sonar modelling.

The term “fusing” refers in this description to combining informationfrom multiple sources to create a data model or combining newinformation with already existing information of a data model to updatethis data model. The multiple sources can be either homogeneous orheterogeneous sources. The information from the multiple sourcestypically has different characteristics, for example the accuracy of thedata, but provides information about the same measured parameters, forexample coordinates describing the position of an object. One reason forfusing information from heterogeneous sources, for example multiplesensors, is to improve the accuracy of the value(s) estimated from themeasured values. The fusion of information can also refer to updatingold information with new information, for example, replacing a locationof a vehicle by its new position. The fusion of information may make useof fusion algorithms. One realisation of the post-processing, orout-of-ground, and equipment models may use a Kalman filter, informationfilter or particle filter for information fusion. However, any otherfusion algorithm may also be applicable.

It will be understood that the invention disclosed and defined in thisspecification extends to all alternative combinations of two or more ofthe individual features mentioned or evident from the text or drawings.All of these different combinations constitute various alternativeaspects of the invention.

TABLE 12 List of acronyms AHT Autonomous Haul Truck AP Access Point BIFBanded Iron Formation CAES Computer Aided Earthmoving System COP CommonOperating Picture HLSA High Level System Architecture ID IdentificationIoA Island of Automation JP Job Planner MAS Mine Automation System MCSMine Control System MP Mine Planner MPC Mine Picture Compilation MPCSMine Picture Compilation System MPS Mine Planning System OEM OriginalEquipment Manufacturer PVA Position, Velocity, Attitude ROC RemoteOperations Centre TP Task Planner UML Unified Modelling Language VPNVirtual Private Network

TABLE 13 Control system terminology Island of A spatial region whoseboundaries are well defined Automation or and which contains specific(discrete) ports for traffic. Island of Autonomy (IoA): xIC: A genericmodule for controlling and coordinating actions within an island ofautomation. Entity: A piece of equipment, machine, person or other“asset” operating in the mine site. Parent: The high-level xICresponsible for the overall task Child: Recursive xIC modules that arestarted and controlled by a parent xIC. Base (B): The current possessorof an entity. Collector or The recipient of an entity Receiver (C):Control List: For an entity, the list of ICs that it is listening to.Note that listening does not necessarily imply execution. Execution isdetermined based on a ranking mechanism. Transition Zone: A userbounded, port location between IoAs for entity transfer and controltransition. It has a continuous area in which an area an entity isallowed to communicate simultaneously with the xIC's. It covers both thexIC's involved in the transfer and straddles the border of their IoAs.Energetic classification of commands: − active: commands the removeenergy from the entity (e.g., braking); passive: commands that do notalter the energy state of the entity (e.g., steering) or; + active:commands that add energy to the entity (e.g., accelerating)

What is claimed is: 1-18. (canceled) 19: A mine automation system,comprising: a memory; a processing unit coupled to the memory; a mineplanning system comprising: a mine planner module coupled to theprocessing unit, wherein the mine planner module is configured togenerate, based on at least one model of a mine region, a plan ofactivities for the mine region, the plan of activities including a firstset of jobs to be performed by autonomous entities; and a locationassociated with each of the jobs; a job planner module coupled to themine planner module, wherein the job planner module is configured toreceive the set of jobs from the mine planner module; and to output ajob plan including a set of tasks for a set of the autonomous entitiesto satisfy each of the jobs, each of the tasks defining the location andone of the autonomous entities to perform the task, wherein the jobplanner module is created using the mine planner module; and a taskplanner module coupled to the job planner module, wherein the taskplanner module is configured to receive the plurality of tasks from thejob planner module and to generate a set of actions for each of theautonomous entities, wherein the task planner module is created usingthe job planner module; a mine control system coupled to the mineplanning system, the mine control system comprising: a plurality ofisland controllers to control a plurality of zones within the mineregion; and a managing controller to control the plurality of Islandcontrollers; a mine analysis system coupled to the mine planning system,the mine analysis system comprising the at least one model of the mineregion, the mine analysis system configured to: receive sensorinformation indicating at least one change within the plurality of zoneswithin the mine region, the at least one change resulting fromimplementation of the set of actions for at least one of the autonomousentities; and update, based on the received sensor information, the atleast one model of the mine region; wherein the mine planning system isconfigured to generate, based on the at least one updated model of themine region, an updated plan of activities for the mine region, theupdated plan of activities including a second set of jobs, differentfrom the first set of jobs, to be performed by autonomous entities. 20:The mine automation system as claimed in claim 19, wherein the mineplanning system further comprises a user interface operable to receivedata from an operator of the mine planning system to define saidlocations. 21: The mine automation system as claimed in claim 19,wherein the mine planning system automatically creates said locationsdependent on the plan of activities for the mine region generated by themine planner module. 22: The mine automation system as claimed in claim19, wherein the mine planning system automatically creates saidlocations dependent on the job plan generated by the job planner module.23: The mine automation system as claimed in claim 19, wherein the planof activities for the mine region comprises production targets for themine region. 24: The mine automation system as claimed in claim 23,wherein the set of jobs comprise activities of entities thatcollectively achieve the production targets. 25: The mine automationsystem as claimed in claim 24, wherein the set of jobs compriseallocation of entities to said locations and allocation of productionactivities to the allocated entities. 26: The mine automation system asclaimed in claim 25, wherein the plurality of tasks comprise movementsor processes required by the allocated entities to complete a saidproduction activity. 27: The mine automation system as claimed in claim19, wherein the mine planning system manages planning instancesimplemented in software, the mine planning instances comprising aplanning instance for each of the jobs and a planning instance for eachsaid task, wherein the mine planning system creates and deletes activeplanning instances to achieve the plan of activities for the mineregion. 28: The mine automation system as claimed in claim 27, whereinthe mine planning system further comprises a communication interfacewith the autonomous entities for receiving status information comprisingthe state of completion of at least one of the jobs and the tasks,wherein the creation and deletion of planning instances is dependent onthe status information. 29: The mine automation system as claimed inclaim 28, wherein managing planning instances comprises: instructions ina planning instance for the mine region for the job planner module tocreate planning instances; and instructions in each planning instancecreated by the job planner module are used by the task planner module tocreate a planning instance. 30: The mine automation system as claimed inclaim 19, wherein the mine planning system and the mine control systemare linked to a mine picture compilation system. 31: The mine automationsystem as claimed in claim 12, wherein the mine planning system isarranged to schedule variation of a geographical disposition of at leastone geographical boundary of a location. 32: The mine automation systemas claimed in claim 9 comprising an interface to receive informationdescribing characteristics of the mine region and comprising a heuristicto automatically create one or more jobs in response to receipt ofparticular information through the interface to receive informationdescribing the characteristics of the mine region. 33: The mineautomation system as claimed in claim 32 comprising an operatorinterface allowing each of the jobs to be modified or deleted by anoperator of the mine planning system. 34: The mine automation system asclaimed in claim 19, wherein the autonomous entities are subject tosupervisory control of the island controllers. 35: The mine automationsystem as claimed in claim 19, wherein the autonomous entities areheterogeneous. 36: The mine planning system of claim 19, wherein the jobplanner module comprises a production planner module and a lower leveljob planner module. 37: The mine planning system of claim 36, whereinthe production planner is configured to generate the set of jobs and thelocation associated with each of the jobs. 38: The mine planning systemof claim 37, wherein the lower level job planner module is configured toreceive the set of jobs from the production planner module and define aset of tasks to satisfy each job, wherein each task specifies thelocation and the autonomous entity to perform the task. 39: The mineplanning system of claim 38, wherein the lower level job planner isconfigured to send each task to the task planner module. 40: The mineplanning system of claim 39, wherein the job planner module furthercomprises one or more intermediate level job planner modules forperforming one or more intermediate jobs.